share objects

------=_Part_2804_400561.1207236741537
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

hi

I have installed static mp2 with apache 2.0.63 (forker). I am using perl
bind (Sleepycat::DBXML) from dbxml; then I create an object (reference to
Sleepycat::DBXML) in startup.pl because i want to share it. After some test
(stress it) for my application I saw some error in error.log; the problem is
that reference to object created in startup.pl was lost

then the question is ... is possible to share objects?


I know I can share data between processes, but what I also shared objects?



thanks in advance

------=_Part_2804_400561.1207236741537
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

hi

I have  installed static mp2 with apache
2.0.63 (forker).  I am using perl bind (Sleepycat::DBXML) from dbxml;
then I create an object (reference to Sleepycat::DBXML) in startup.pl
because i want to share it. After some test (stress it) for my
application I saw some error in error.log; the problem is that
reference to object created in startup.pl was lost


then the question is ... is possible to share objects?


I know I can share data between processes, but what I also shared objects?



thanks in advance


------=_Part_2804_400561.1207236741537--

Re: share objects

On Thu, Apr 3, 2008 at 11:32 PM, Felipe de Jes=FAs Molina Bravo
wrote:
> hi
>
> I have installed static mp2 with apache 2.0.63 (forker). I am using per=
l
> bind (Sleepycat::DBXML) from dbxml; then I create an object (reference to
> Sleepycat::DBXML) in startup.pl because i want to share it. After some te=
st
> (stress it) for my application I saw some error in error.log; the problem=
is
> that reference to object created in startup.pl was lost
>
> then the question is ... is possible to share objects?
>

If your object has its own package name space, you can share it
between multi-processes.
But if you state this in startup.pl,

my $obj =3D Sleepycat::DBXML->new();

this $obj can't be shared among multi-processes. Because it doesn't
have its package name space.

So,you'd better write a package to encap that object, like:

package MyPKG;
use strict;
use Sleepycat::DBXML;

our $obj =3D Sleepycat::DBXML->new;
sub initobj { $obj }

1;

And put 'use MyPKG' in the startup.pl.
then in your scripts you can access this object by saying 'our $obj'
or via the method of 'my $obj =3D MyPKG->initobj'.

Good luck.

Re: share objects

On Thu, Apr 3, 2008 at 11:32 AM, Felipe de Jes=FAs Molina Bravo
wrote:
> I know I can share data between processes, but what I also shared objects=
?

It depends on what you mean by share. You can create a simple perl
object in startup.pl and access it from all processes later, but if
you change it in one process, the change will not be seen in the
others. With objects that contain open sockets, file handles, or XS
structures, you usually can't share them at all. This is why you
can't open a DBI connection in startup and use it from your child
processes.

I don't know Sleepycat::DBXML, but it sounds like something that would
use file handles. Try creating your object in a PerlInitHandler
instead, which runs in the child process when it is first created.

- Perrin

Re: share objects

------=_Part_3311_20894592.1207243059918
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2008/4/3, Jeff Pang :
>
> On Thu, Apr 3, 2008 at 11:32 PM, Felipe de Jes=FAs Molina Bravo
> wrote:
> > hi
> >
> > I have installed static mp2 with apache 2.0.63 (forker). I am using
> perl
> > bind (Sleepycat::DBXML) from dbxml; then I create an object (reference
> to
> > Sleepycat::DBXML) in startup.pl because i want to share it. After some
> test
> > (stress it) for my application I saw some error in error.log; the
> problem is
> > that reference to object created in startup.pl was lost
> >
> > then the question is ... is possible to share objects?
> >
>
>
> If your object has its own package name space, you can share it
> between multi-processes.
> But if you state this in startup.pl,
>
> my $obj =3D Sleepycat::DBXML->new();
>
> this $obj can't be shared among multi-processes. Because it doesn't
> have its package name space.
>
> So,you'd better write a package to encap that object, like:
>
> package MyPKG;
> use strict;
> use Sleepycat::DBXML;
>
> our $obj =3D Sleepycat::DBXML->new;
> sub initobj { $obj }
>
> 1;
>
> And put 'use MyPKG' in the startup.pl.
> then in your scripts you can access this object by saying 'our $obj'
> or via the method of 'my $obj =3D MyPKG->initobj'.
>
> Good luck.
>

thanks a lot

My problem was solved ... The problem was that I had the buildup of the
object (new) within "sub initobj () "

regards

------=_Part_3311_20894592.1207243059918
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Re: share objects

------=_Part_3364_25270428.1207244034283
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2008/4/3, Perrin Harkins :
>
> On Thu, Apr 3, 2008 at 11:32 AM, Felipe de Jes=FAs Molina Bravo
> wrote:
>
> > I know I can share data between processes, but what I also shared
> objects?
>
>
> It depends on what you mean by share. You can create a simple perl
> object in startup.pl and access it from all processes later, but if
> you change it in one process, the change will not be seen in the
> others. With objects that contain open sockets, file handles, or XS
> structures, you usually can't share them at all.


Is when they can be shared? and if my file handle is open of "ro" .... it
can share between process?


This is why you
> can't open a DBI connection in startup and use it from your child
> processes.
>
> I don't know Sleepycat::DBXML, but it sounds like something that would
> use file handles. Try creating your object in a PerlInitHandler
> instead, which runs in the child process when it is first created.

- Perrin
>

Thanks ...
best regards

felipe

------=_Part_3364_25270428.1207244034283
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Re: share objects

On Thu, Apr 3, 2008 at 1:33 PM, Felipe de Jes=FAs Molina Bravo
wrote:
> > It depends on what you mean by share. You can create a simple perl
> > object in startup.pl and access it from all processes later, but if
> > you change it in one process, the change will not be seen in the
> > others. With objects that contain open sockets, file handles, or XS
> > structures, you usually can't share them at all.
>
> Is when they can be shared? and if my file handle is open of "ro" .... =
it
> can share between process?

It can be done, but it's tricky. When you try to use one file handle
from multiple process it gets confused about the location in the file.
If you really need to do it, read about shared file handles in
Programming Perl or your favorite Unix reference.

- Perrin

Re: share objects

------=_Part_4163_1491849.1207253867081
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2008/4/3, Perrin Harkins :
>
> On Thu, Apr 3, 2008 at 1:33 PM, Felipe de Jes=FAs Molina Bravo
> wrote:
> > > It depends on what you mean by share. You can create a simple perl
> > > object in startup.pl and access it from all processes later, but if
> > > you change it in one process, the change will not be seen in the
> > > others. With objects that contain open sockets, file handles, or XS
> > > structures, you usually can't share them at all.
> >
> > Is when they can be shared? and if my file handle is open of "ro" ...=
..
> it
> > can share between process?
>
>
> It can be done, but it's tricky. When you try to use one file handle
> from multiple process it gets confused about the location in the file.
> If you really need to do it, read about shared file handles in
> Programming Perl or your favorite Unix reference.
>
>
> - Perrin
>

ok ...thanks a lot


regards
felipe

------=_Part_4163_1491849.1207253867081
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline